suddedenly increased in size of Log files form 32GB to 70 GB I am not DBA ,but I need to check on the size of database files .
my database log files earlier was around 32 GB but from last few days it starts increasing and finally reached to 70 GB . first I thought it was natural , but soon I realized  that I was wrong  .

For shrinking the size of log file ,firstly I used to determine the % of space occupied in log file  by using .

        DBCC SQLPERF(logspace)


Result was :- log size(MB) > 70 and Log Space Used > 94%
 with 

          DBCC LOGINFO


I found more than 700 transactions having Status = '2'

After that I took "log as well as full backup" 
and run above query again but still got >700  transactions having Status = '2'
detached and reattached , but still no difference in size .

Then I went for Shrinking log files and for testing purpose I gave the size 60GB .
 Then run following query again 

   DBCC SQLPERF(logspace)


and result was :- log size(MB) > 66 and Log Space Used =  99.1258%.

Question is : How can I bring the size of log files near to earlier size i.e. around 32 GB or near by and how to keep check on it so that its size does not change dramatically .

** Recovery Mode :- FULL 

Thanks in advance ....
A full database backup won't help your log size. 

Full Recovery Model means "Can restore to any point in time." - including before that new database backup was taken. 

Simple Recovery Model means "Can restore to the last database backup".

So... have a think about whether you need to restore to this morning or not (before your database backup). If you don't, then put your database into Simple Recovery Model, then back into Full. Then take a differential backup. Once you've done those three steps you will be able to recover to your last full database backup, the differential backup you just took, and any point in the future. Take regular log backups - try every ten-to-fifteen minutes.

And then look at your log. You should find it's mostly empty.

If not, look in sys.databases to see why it's not truncating. Other possible reasons include Replication that's broken, for example.